SUPPORT / SAMPLES & SAS NOTES
Problem Note 57252: Scheduling does not work with jobs that use a one-time password security context
 |  |  |  |  |
When a job that uses a one-time password security context (for example, SAS® Model Manager) calls a scheduler, the job trigger fails. The problem occurs because the Principal object (which refers to the user ID or user name for the associated user in the security domain) incorrectly contains a generated password domain. As a result, the Job Execution Service cannot re-create the security context, and the job fails. This problem happens when you use the Distributed In-Process Scheduler, the Platform Scheduler, or your operating-system scheduler.
When the problem occurs, the following exception error is generated:
Unable to trigger scheduled job[ID=6437de03-0a15-0cbd-27ab-5d8ff4107e3d]
com.sas.svcs.jobexecution.client.JobException: org.springframework.security.authentication.InsufficientAuthenticationException: Unable to create a user context for user: edmdev@!*(generatedpassworddomain)*!
at com.sas.svcs.jobexecution.impl.JobManager.triggerScheduledJob(JobManager.java:1129)
at com.sas.svcs.jobexecution.scheduling.DistributedIPJobRunner.runJob(DistributedIPJobRunner.java:199)
at com.sas.scheduler.api.servers.ip.engine.mq.client.JMSClientSupport$4$2.run(JMSClientSupport.java:650)
at com.sas.scheduler.api.servers.ip.engine.threadpool.WorkerThread.doCurrentWorkNow(WorkerThread.java:151)
at com.sas.scheduler.api.servers.ip.engine.threadpool.WorkerThread.run(WorkerThread.java:195)
Caused by: org.springframework.security.authentication.InsufficientAuthenticationException: Unable to create a user context for user: edmdev@!*(generatedpassworddomain)*!
at com.sas.svcs.authorization.impl.MetadataUserDetailsServiceWrapper.loadUserByUsername(MetadataUserDetailsServiceWrapper.java:142)
at sun.reflect.GeneratedMethodAccessor822.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at org.springframework.security.access.intercept.aopalliance.MethodSecurityInterceptor.invoke(MethodSecurityInterceptor.java:61)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
. . .more message lines. . .
*******Data truncated by client for dialog display*******
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Web Infrastructure Platform | Solaris for x64 | 9.4_M3 | 9.4_M4 | 9.4 TS1M3 | 9.4 TS1M4 |
| Linux for x64 | 9.4_M3 | 9.4_M4 | 9.4 TS1M3 | 9.4 TS1M4 | ||
| HP-UX IPF | 9.4_M3 | 9.4_M4 | 9.4 TS1M3 | 9.4 TS1M4 | ||
| 64-bit Enabled Solaris | 9.4_M3 | 9.4_M4 | 9.4 TS1M3 | 9.4 TS1M4 | ||
| 64-bit Enabled AIX | 9.4_M3 | 9.4_M4 | 9.4 TS1M3 | 9.4 TS1M4 | ||
| Microsoft® Windows® for x64 | 9.4_M3 | 9.4_M4 | 9.4 TS1M3 | 9.4 TS1M4 | ||